Miniature Comet Ice and Dust Experiment (Mini-CIDEX)

This document reports the extent of the progress attained by Lockheed Martin Astronautics (LMA) in the development of equipment designed for the miniature Comet Ice and Dust EXperiment (mini-CIDEX) on NASA contract No. NAS2-14042 from the Ames Research Center (ARC). This report is in two parts. The first part summarizes progress in chronological order. The contents of the first part have been extracted from the monthly reports submitted by LMA to ARC over the duration of the program. The second part is a summary of the designs that were extracted from the mini-CIDEX contract designs and implemented into mission studies performed under different funding but in parallel to the mini- CIDEX contract time period. These second part activities were not performed under contract No. NAS2-14042; however, they are included in this report to show how it was intended that the mini-CIDEX be used on actual mission spacecraft

On Using SysML, DoDAF 2.0 and UPDM to Model the Architecture for the NOAA's Joint Polar Satellite System (JPSS) Ground System (GS)

The JPSS Ground System is a lIexible system of systems responsible for telemetry, tracking & command (TT &C), data acquisition, routing and data processing services for a varied lIeet of satellites to support weather prediction, modeling and climate modeling. To assist in this engineering effort, architecture modeling tools are being employed to translate the former NPOESS baseline to the new JPSS baseline, The paper will focus on the methodology for the system engineering process and the use of these architecture modeling tools within that process, The Department of Defense Architecture Framework version 2,0 (DoDAF 2.0) viewpoints and views that are being used to describe the JPSS GS architecture are discussed. The Unified Profile for DoOAF and MODAF (UPDM) and Systems Modeling Language (SysML), as ' provided by extensions to the MagicDraw UML modeling tool, are used to develop the diagrams and tables that make up the architecture model. The model development process and structure are discussed, examples are shown, and details of handling the complexities of a large System of Systems (SoS), such as the JPSS GS, with an equally complex modeling tool, are describe

Architecting Communication Network of Networks for Space System of Systems

The National Aeronautics and Space Administration (NASA) and the Department of Defense (DoD) are planning Space System of Systems (SoS) to address the new challenges of space exploration, defense, communications, navigation, Earth observation, and science. In addition, these complex systems must provide interoperability, enhanced reliability, common interfaces, dynamic operations, and autonomy in system management. Both NASA and the DoD have chosen to meet the new demands with high data rate communication systems and space Internet technologies that bring Internet Protocols (IP), routers, servers, software, and interfaces to space networks to enable as much autonomous operation of those networks as possible. These technologies reduce the cost of operations and, with higher bandwidths, support the expected voice, video, and data needed to coordinate activities at each stage of an exploration mission. In this paper, we discuss, in a generic fashion, how the architectural approaches and processes are being developed and used for defining a hypothetical communication and navigation networks infrastructure to support lunar exploration. Examples are given of the products generated by the architecture development process

Liposomal Bupivacaine in Total Knee Arthroplasty: Preliminary Results of a Two-Surgeon, Retrospective Study

INTRODUCTION: Liposomal bupivacaine (LB) is a slowly degrading preparation that provides local anesthesia for up to 72 hours. It targets the site directly responsible for pain sensation, with no associated motor blockade. In total knee arthroplasty (TKA), it may have superior outcomes to anesthesia with regional nerve block. METHODS: Our surgeons began using LB in TKA patients in 2013. All patients following each surgeon’s LB start date were the experimental group. An equivalent number of patients prior to 2013 served as the control group. All control group patients received a preoperative femoral nerve block, and all experimental group patients received peri- and intra-articular LB, delivered intraoperatively. All other surgical and anesthesia interventions were the same. We used retrospective chart review to identify patient demographics, time to first ambulation, time to discharge, and incidence of postoperative nausea and vomiting. We also recorded opioid consumption intraoperatively, in the recovery room, and on the floor. RESULTS: There were 161 patients in each group. We found no significant difference between the two groups with regard to gender, age, weight, preoperative opioid exposure, side of procedure, type of anesthesia (general vs. spinal), or ASA status. On average, LB patients consumed 29.2% less opioid after leaving the recovery room (p DISCUSSION AND CONCLUSION: With increasing focus on the cost of TKA, there is strong incentive to manage costs associated with the procedure. Additionally, all patients, regardless of comorbid conditions, can benefit from limited exposure to narcotic pain medication. Our results indicate that LB decreases total systemic opioid requirement, time to first ambulation, and time to discharge from the hospital

Integrated Network Architecture for NASA's Orion Missions

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. The series of missions will begin with a new crew exploration vehicle (called Orion) that will initially provide crew exchange and cargo supply support to the International Space Station (ISS) and then become a human conveyance for travel to the Moon. The Orion vehicle will be mounted atop the Ares I launch vehicle for a series of pre-launch tests and then launched and inserted into low Earth orbit (LEO) for crew exchange missions to the ISS. The Orion and Ares I comprise the initial vehicles in the Constellation system of systems that later includes Ares V, Earth departure stage, lunar lander, and other lunar surface systems for the lunar exploration missions. These key systems will enable the lunar surface exploration missions to be initiated in 2018. The complexity of the Constellation system of systems and missions will require a communication and navigation infrastructure to provide low and high rate forward and return communication services, tracking services, and ground network services. The infrastructure must provide robust, reliable, safe, sustainable, and autonomous operations at minimum cost while maximizing the exploration capabilities and science return. The infrastructure will be based on a network of networks architecture that will integrate NASA legacy communication, modified elements, and navigation systems. New networks will be added to extend communication, navigation, and timing services for the Moon missions. Internet protocol (IP) and network management systems within the networks will enable interoperability throughout the Constellation system of systems. An integrated network architecture has developed based on the emerging Constellation requirements for Orion missions. The architecture, as presented in this paper, addresses the early Orion missions to the ISS with communication, navigation, and network services over five phases of a mission: pre-launch, launch from T0 to T+6.5 min, launch from T+6.5 min to 12 min, in LEO for rendezvous and docking with ISS, and return to Earth. The network of networks that supports the mission during each of these phases and the concepts of operations during those phases are developed as a high level operational concepts graphic called OV-1, an architecture diagram type described in the Department of Defense Architecture Framework (DoDAF). Additional operational views on organizational relationships (OV-4), operational activities (OV-5), and operational node connectivity (OV-2) are also discussed. The system interfaces view (SV-1) that provides the communication and navigation services to Orion is also included and described. The challenges of architecting integrated network architecture for the NASA Orion missions are highlighted

Lunar Relay Satellite Network for Space Exploration: Architecture, Technologies and Challenges

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. A key objective of these missions is to grow, through a series of launches, a system of systems infrastructure with the capability for safe and sustainable autonomous operations at minimum cost while maximizing the exploration capabilities and science return. An incremental implementation process will enable a buildup of the communication, navigation, networking, computing, and informatics architectures to support human exploration missions in the vicinities and on the surfaces of the Moon and Mars. These architectures will support all space and surface nodes, including other orbiters, lander vehicles, humans in spacesuits, robots, rovers, human habitats, and pressurized vehicles. This paper describes the integration of an innovative MAC and networking technology with an equally innovative position-dependent, data routing, network technology. The MAC technology provides the relay spacecraft with the capability to autonomously discover neighbor spacecraft and surface nodes, establish variable-rate links and communicate simultaneously with multiple in-space and surface clients at varying and rapidly changing distances while making optimum use of the available power. The networking technology uses attitude sensors, a time synchronization protocol and occasional orbit-corrections to maintain awareness of its instantaneous position and attitude in space as well as the orbital or surface location of its communication clients. A position-dependent data routing capability is used in the communication relay satellites to handle the movement of data among any of multiple clients (including Earth) that may be simultaneously in view; and if not in view, the relay will temporarily store the data from a client source and download it when the destination client comes into view. The integration of the MAC and data routing networking technologies would enable a relay satellite system to provide end-to-end communication services for robotic and human missions in the vicinity, or on the surface of the Moon with a minimum of Earth-based operational support

Genome evolution and host‐microbiome shifts correspond with intraspecific niche divergence within harmful algal bloom‐forming Microcystis aeruginosa

Intraspecific niche divergence is an important driver of species range, population abundance and impacts on ecosystem functions. Genetic changes are the primary focus when studying intraspecific divergence; however, the role of ecological interactions, particularly host‐microbiome symbioses, is receiving increased attention. The relative importance of these evolutionary and ecological mechanisms has seen only limited evaluation. To address this question, we used Microcystis aeruginosa, the globally distributed cyanobacterium that dominates freshwater harmful algal blooms. These blooms have been increasing in occurrence and intensity worldwide, causing major economic and ecological damages. We evaluated 46 isolates of M. aeruginosa and their microbiomes, collected from 14 lakes in Michigan, USA, that vary over 20‐fold in phosphorus levels, the primary limiting nutrient in freshwater systems. Genomes of M. aeruginosa diverged along this phosphorus gradient in genomic architecture and protein functions. Fitness in low‐phosphorus lakes corresponded with additional shifts within M. aeruginosa including genome‐wide reductions in nitrogen use, an expansion of phosphorus assimilation genes and an alternative life history strategy of nonclonal colony formation. In addition to host shifts, despite culturing in common‐garden conditions, host‐microbiomes diverged along the gradient in taxonomy, but converged in function with evidence of metabolic interdependence between the host and its microbiome. Divergence corresponded with a physiological trade‐off between fitness in low‐phosphorus environments and growth rate in phosphorus‐rich conditions. Co‐occurrence of genotypes adapted to different nutrient environments in phosphorus‐rich lakes may have critical implications for understanding how M. aeruginosa blooms persist after initial nutrient depletion. Ultimately, we demonstrate that the intertwined effects of genome evolution, host life history strategy and ecological interactions between a host and its microbiome correspond with an intraspecific niche shift with important implications for whole ecosystem function.Peer Reviewedhttps://deepblue.lib.umich.edu/bitstream/2027.42/151861/1/mec15198_am.pdfhttps://deepblue.lib.umich.edu/bitstream/2027.42/151861/2/mec15198.pdfhttps://deepblue.lib.umich.edu/bitstream/2027.42/151861/3/mec15198-sup-0001-Supinfo.pd

The current state of antifungal stewardship among pediatric antimicrobial stewardship programs

OBJECTIVE: To characterize the current state of antifungal stewardship practices and perceptions of antifungal use among pediatric antimicrobial stewardship programs (ASPs). DESIGN: We developed and distributed an electronic survey, which included 17 closed-ended questions about institutional antifungal stewardship practices and perceptions, among pediatric ASPs. PARTICIPANTS: ASP physicians and pharmacists of 74 hospitals participating in the multicenter Sharing Antimicrobial Reports for Pediatric Stewardship (SHARPS) Collaborative. RESULTS: We sent surveys to 74 hospitals and received 68 unique responses, for a response rate of 92%. Overall, 63 of 68 the respondent ASPs (93%) reported that they conduct 1 or more antifungal stewardship activities. Of these 68 hospital ASPs, 43 (63%) perform prospective audit and feedback (PAF) of antifungals. The most common reasons reported for not performing PAF of antifungals were not enough time or resources (19 of 25, 76%) and minimal institutional antifungal use (6 of 25, 24%). Also, 52 hospitals (76%) require preauthorization for 1 or more antifungal agents. The most commonly restricted antifungals were isavuconazole (42 of 52 hospitals, 80%) and posaconazole (39 of 52 hospitals, 75%). Furthermore, 33 ASPs (48%) agreed or strongly agreed that antifungals are inappropriately used at their institution, and only 25 of 68 (37%) of ASPs felt very confident making recommendations about antifungals. CONCLUSIONS: Most pediatric ASPs steward antifungals, but the strategies employed are highly variable across surveyed institutions. Although nearly half of respondents identified inappropriate antifungal use as a problem at their institution, most ASPs do not feel confident making recommendations about antifungals. Future studies are needed to determine the rate of inappropriate antifungal use and the best antifungal stewardship strategies

Surface Communications Network Architectures for Exploration Missions

contents include the following: 1. Requirements: Missions. Infrastructure. End-to-End. 2. Operational View: System View. Nodes. Interfaces. Links. Network Design. Technologies

Characteristics of antifungal utilization for hospitalized children in the United States

OBJECTIVE: To characterize antifungal prescribing patterns, including the indication for antifungal use, in hospitalized children across the United States. DESIGN: We analyzed antifungal prescribing data from 32 hospitals that participated in the SHARPS Antibiotic Resistance, Prescribing, and Efficacy among Children (SHARPEC) study, a cross-sectional point-prevalence survey conducted between June 2016 and December 2017. METHODS: Inpatients aged \u3c18 years with an active systemic antifungal order were included in the analysis. We classified antifungal prescribing by indication (ie, prophylaxis, empiric, targeted), and we compared the proportion of patients in each category based on patient and antifungal characteristics. RESULTS: Among 34,927 surveyed patients, 2,095 (6%) received at least 1 systemic antifungal and there were 2,207 antifungal prescriptions. Most patients had an underlying oncology or bone marrow transplant diagnosis (57%) or were premature (13%). The most prescribed antifungal was fluconazole (48%) and the most common indication for antifungal use was prophylaxis (64%). Of 2,095 patients receiving antifungals, 79 (4%) were prescribed \u3e1 antifungal, most often as targeted therapy (48%). The antifungal prescribing rate ranged from 13.6 to 131.2 antifungals per 1,000 patients across hospitals ( CONCLUSIONS: Most antifungal use in hospitalized children was for prophylaxis, and the rate of antifungal prescribing varied significantly across hospitals. Potential targets for antifungal stewardship efforts include high-risk, high-utilization populations, such as oncology and bone marrow transplant patients, and specific patterns of utilization, including prophylactic and combination antifungal therapy